Module 5, Section 2: Presentation Design & Storytelling

1.1 The SCQA Framework ⏱️ 5 min

🎯 Learning Objective

Master McKinsey's SCQA storytelling framework for compelling sales presentations.

The best sales presentations aren't feature lists—they're stories. McKinsey consultants use the SCQA framework to structure every client presentation. Here's why it works:

S - Situation

The current state. Facts everyone agrees on.

"You process 50,000 loans monthly..."

→

C - Complication

The problem. What changed or went wrong.

"...but NPAs increased 15% this year."

→

Q - Question

The implicit question raised by the complication.

"How do you predict and prevent NPAs?"

→

A - Answer

Your solution. The payoff.

"Tantor predicts NPAs 6 months early."

Why SCQA Works

Creates tension: Situation + Complication builds urgency
Makes them think: Question engages their brain before you give the answer
Positions you as the solution: Answer feels like a natural resolution
Mirrors how humans process stories: Setup → Conflict → Resolution

⚠️ Common Mistake: Jumping straight to the Answer. "Let me tell you about Tantor's features..." skips the story. Without Situation and Complication, your Answer has no context or urgency.

1.2 SCQA Applied to Translab ⏱️ 5 min

🎯 Learning Objective

Build SCQA narratives for different Translab products and scenarios.

SCQA Examples by Product

Tantor AI Platform (Banking)

S: "Your bank has ₹2,000 Cr in loan portfolio across 50,000 accounts."
C: "NPA ratio increased from 3.2% to 5.1% this year—₹38 Cr at risk."
Q: "How do you identify at-risk accounts before they become NPAs?"
A: "Tantor's NPA Prediction Agent identifies high-risk accounts 6 months early, reducing provisions by 30%."

Kong API Gateway

S: "You're running 500+ microservices across 3 cloud regions."
C: "Last month, an unthrottled API caused a cascade failure during peak traffic—2 hours of downtime."
Q: "How do you prevent one rogue service from taking down your entire system?"
A: "Kong provides circuit breakers, rate limiting, and real-time observability—preventing cascade failures."

🎮 Build Your Own SCQA

Scenario: You're pitching HashiCorp Terraform to a bank struggling with multi-cloud infrastructure.

Drag each element to the correct SCQA slot:

Your IT team manages infrastructure across AWS, Azure, and on-prem

Provisioning a new environment takes 3 weeks and 47 manual steps

How do you provision infrastructure in minutes, not weeks?

Terraform provisions multi-cloud infrastructure with one command

S - Situation

C - Complication

Q - Question

A - Answer

💡 Why This SCQA Works

Situation: Establishes complexity (3 environments) without judgment
Complication: Quantifies the pain (3 weeks, 47 steps)—makes it real
Question: Frames the problem in their terms (speed, not technology)
Answer: Direct response to the question—positions Terraform as the solution

Pro tip: Notice the question asks about their outcome (fast provisioning), not about Terraform. This keeps the focus on them, not you.

2.1 Action Titles vs Descriptive Titles ⏱️ 5 min

🎯 Learning Objective

Write slide titles that state conclusions, not descriptions.

The McKinsey Rule: Every Slide Title Should Be a Headline

If an executive reads only your slide titles, they should understand your entire argument.

❌ Descriptive Title:
"NPA Analysis Overview"
Tells you the topic, not the insight

✅ Action Title:
"NPAs Will Increase 25% Without Early Detection"
States the conclusion—compelling and actionable

More Examples

❌ Descriptive		✅ Action Title
"Market Overview"	→	"Digital Lending Market Will Reach ₹5 Trillion by 2026"
"Solution Architecture"	→	"Tantor Integrates All Data Sources in Real-Time Without ETL"
"ROI Analysis"	→	"Expected ROI: ₹15 Cr Savings in Year 1"
"Implementation Timeline"	→	"Go-Live in 8 Weeks with Zero Disruption"

🔧 Fix These Titles

Select the best action title replacement for each descriptive title:

❌ "Tantor AI Platform Features"

Tantor AI Platform: Key Capabilities and Benefits

Tantor Reduces NPA Provisions by 30% with 6-Month Early Warning

Overview of AI-Powered Risk Management Solutions

❌ "API Gateway Comparison"

Comparing Kong vs Competitors: Feature Analysis

API Gateway Market Landscape

Kong Handles 10x Traffic Spikes with 50% Lower Latency than Alternatives

💡 The Action Title Formula

Structure: [Subject] + [Verb] + [Quantified Outcome]

"Tantor reduces NPA provisions by 30%"
"Kong handles 10x traffic with 50% lower latency"

Test: Can an executive read just your titles and understand your proposal? If yes, you've nailed it.

2.2 Visual Design Principles ⏱️ 5 min

🎯 Learning Objective

Apply consulting-grade visual design principles to sales slides.

The 6 Principles of Effective Slide Design

One Message Per Slide: If you need two points, make two slides
Signal-to-Noise Ratio: Remove everything that doesn't support the message
Data Visualization: Charts > Tables > Text for numbers
Action Titles: State conclusions in titles (covered in 2.1)
Visual Hierarchy: Eye flow: Title → Visual → Supporting text
Consistent Branding: Colors, fonts, logo placement

Signal-to-Noise: The #1 Mistake

❌ High Noise Slide

Title: "Tantor Data Platform Connectors"

"Tantor Data Platform provides 50+ connectors including Oracle, SQL Server, MySQL, PostgreSQL, MongoDB, Cassandra, Kafka, S3, Azure Blob Storage, Google Cloud Storage, Snowflake, Redshift, BigQuery, Databricks, Elasticsearch, Salesforce, SAP, Workday..."

Problem: Cognitive overload. Prospect remembers nothing.

✅ High Signal Slide

Title: "Tantor Connects to All Your Systems—No New ETL"

Visual: 3 icons showing "Core Banking → Tantor → Analytics"

Subtext: "50+ pre-built connectors. Your Oracle, Salesforce, and data warehouse—unified in real-time."

Why it works: Simple visual, clear benefit, details available if asked.

🔎 Spot the Design Violation

Which slide violates visual design principles? Click the violator:

Slide A

Title: "Implementation Takes 8 Weeks"

Visual: Timeline graphic showing 4 phases

One clear message, visual supports it

Slide B

Title: "Solution Overview"

Contains: Architecture diagram + Feature list + ROI table + Customer logos + Implementation timeline

Slide C

Title: "Kong Reduces Latency 50% vs Legacy Gateways"

Visual: Bar chart comparing response times

Data visualization supports the claim

💡 Why Slide B Fails

Violates "One Message Per Slide": 5 different elements competing for attention
Violates "Signal-to-Noise": Too much information = nothing stands out
Descriptive title: "Solution Overview" says nothing specific

The fix: Split into 5 slides, each with one clear message and action title.

💡 The Squint Test: Squint at your slide from across the room. If you can't tell what it's about, there's too much noise.

3.1 Tech-to-Business Translation ⏱️ 5 min

🎯 Learning Objective

Translate technical features into business outcomes that resonate with buyers.

The Translation Formula

[Technical Feature] → [So What?] → [Business Outcome]

Example: "Log-based CDC" → "Real-time data sync" → "Detect fraud in seconds, not hours"

Translab Product Translation Table

Product	Technical Feature		Business Outcome
Tantor Data	Log-based CDC with sub-second latency	→	Detect fraud in real-time, preventing ₹50L daily losses
Tantor AI	20+ pre-trained AI agents with AutoML	→	Launch NPA prediction in 4 weeks, not 6 months
Kong	Circuit breaker pattern with health checks	→	99.99% uptime during Diwali sale traffic surge
DataStax	Vector search with ANN algorithms	→	GenAI chatbot responds in <200ms, improving CSAT 40%
HashiCorp	Infrastructure-as-code with state management	→	Provision AWS+Azure+GCP in 10 minutes, not 3 weeks
Cloudera	Self-service data provisioning with SDX	→	Data analysts get clusters in 10 min, not 3 days
Managed Services	24/7 NOC with proactive monitoring	→	Zero production outages, 99.9% SLA guarantee

⚠️ Common Mistake: Stopping at the technical feature. "We have log-based CDC" means nothing to a CFO. "Detect fraud in real-time" speaks to their P&L.

3.2 Translation Practice ⏱️ 5 min

🎯 Learning Objective

Practice translating technical features into business outcomes.

🎮 Match the Translation

Drag each technical feature to its correct business translation:

"Sub-second data replication"

"Automated regulatory reporting"

"Multi-region failover"

"Pre-built ML models"

💰 "Catch fraud before money leaves the bank"

📋 "Submit RBI reports in hours, not weeks"

🔒 "Stay online even if an entire data center fails"

🚀 "Deploy AI in weeks, not months"

💡 Translation Logic

Technical	Business	Why
Sub-second replication	Catch fraud before money leaves	Speed enables real-time fraud detection
Automated reporting	Submit RBI reports in hours	Automation removes manual bottlenecks
Multi-region failover	Stay online if DC fails	Redundancy = availability
Pre-built ML models	Deploy AI in weeks	No need to build from scratch

Write Your Own Translation

Challenge: Translate this technical feature into a business outcome:

Technical: "Tantor's data fabric provides virtual data layer without physical replication"

Your business translation:

4.1 Executive Presentation Style ⏱️ 5 min

🎯 Learning Objective

Adapt your presentation style for CFOs, CEOs, and COOs.

The Executive Buyer Profile

Who: CFO, CEO, COO, VP Finance, Board Members

Time: 10-15 minutes max (they'll leave if you ramble)

What They Care About: ROI, risk, competitive advantage, strategic fit

What They Don't Care About: Technical architecture, API specs, database schemas

Executive Presentation Rules

✅ Do This

Lead with business impact (₹ saved, % improved)
State ROI in first 2 minutes
Use peer validation ("HDFC did this...")
Keep slides sparse (8-10 max)
Answer "So what?" on every slide
End with clear decision ask

❌ Don't Do This

Start with architecture diagrams
Use technical jargon (CDC, API, SDK)
Show every feature
Bury ROI at the end
Present for 45+ minutes
End with "Any questions?"

🎬 Scenario: CFO Opens Your Meeting

You're presenting Tantor to a CFO. She says: "I have 15 minutes. What do you have for me?"

What's your opening line?

Option A

"Let me start by introducing Translab and our history in the banking sector..."

Option B

"I'll walk you through our data platform architecture and how it integrates with your systems..."

Option C

"Your NPA provisions cost ₹38Cr last year. We can reduce that by 30%—let me show you how in 10 minutes."

Option D

"Great question—what would you like to cover first?"

💡 Why Option C Wins

Opens with THEIR number: "₹38Cr" shows you did homework
States the outcome: "30% reduction" is the headline
Respects their time: "10 minutes" shows you're efficient
Creates urgency: Money on the table they're leaving behind

Why others fail:

A: Company history = wastes time, self-focused
B: Architecture = wrong audience, too technical
D: Defers to them = you lose control, looks unprepared

4.2 Technical Presentation Style ⏱️ 5 min

🎯 Learning Objective

Adapt your presentation style for CTOs, architects, and engineering leads.

The Technical Buyer Profile

Who: CTO, CIO, VP Engineering, Lead Architect, DevOps Lead

Time: 20-30 minutes (they'll ask detailed questions)

What They Care About: Architecture, scalability, security, integration, maintenance

What They Don't Care About: Marketing fluff, vague ROI claims without proof

Technical Presentation Rules

✅ Do This

Show architecture diagrams early
Provide technical specs (latency, throughput)
Demonstrate integrations live
Discuss security and compliance
Be honest about limitations
Share API docs, SDKs, documentation

❌ Don't Do This

Oversimplify for a technical audience
Make claims you can't prove technically
Hide limitations (they'll find them)
Skip the "how it works"
Use only business metrics
Dismiss technical questions

Same Product, Different Angle

Tantor Data Platform: Executive vs Technical

Aspect	Executive Version	Technical Version
Opening	"Reduce data integration costs 40%"	"Log-based CDC with <100ms latency"
Visual	ROI calculator, savings chart	Architecture diagram, data flow
Proof	Customer logo, case study quote	Benchmark results, security certs
Questions	"When can we see ROI?"	"How does it handle schema changes?"

💡 Pro Tip: In mixed meetings (CFO + CTO), use the "layered approach": Start with business impact (2 min), then go technical (10 min), close with ROI (2 min). The CFO gets their headline, the CTO gets their details.

5.1 Slides-to-Demo Ratio ⏱️ 5 min

🎯 Learning Objective

Know the optimal balance between slides and live demo for each product.

The General Rule

Technical products → More demo (seeing is believing)

Services → More slides (trust is built through process, not screens)

Product-Specific Ratios

Product	Slides : Demo	Visual	Why
Tantor Data Platform	30% : 70%	30% 70%	Technical buyers need to see real-time data flow
Tantor AI Platform	40% : 60%	40% 60%	AI needs context (slides), then proof (demo)
Kong API Gateway	25% : 75%	25% 75%	Developers want to see APIs and configs live
DataStax Astra DB	30% : 70%	30% 70%	Vector search performance needs live proof
HashiCorp Terraform	20% : 80%	20% 80%	Infrastructure-as-code = show the code running
Cloudera	35% : 65%	35% 65%	Self-service needs demo, but ROI story needs slides
Managed Services	70% : 30%	70% 30%	Services = trust in process, team, SLAs
Professional Services	80% : 20%	80% 20%	Consulting = methodology, team, past success

⚠️ Common Mistake: Jumping into demo without context. "Let me show you Tantor" means nothing. Instead: "Your Basel III reports take 10 days. Let me show you how we get that to 4 hours" = context + demo.

5.2 Handling Demo Failures ⏱️ 5 min

🎯 Learning Objective

Recover gracefully when demos crash—without losing credibility.

⚠️ Reality Check: Demo environments fail. Networks drop. Browsers crash. The question isn't IF it happens, but WHEN—and how you handle it.

The 3 Fallback Options

Option 1: Pre-Recorded Demo (Best)

Always have a video recording of your demo ready
Script: "The live environment is having issues—let me show you our recorded demo with actual customer data"
Advantage: Smooth, edited, shows best-case scenario

Option 2: Screenshot Walkthrough

Have slides with screenshots of key demo moments
Script: "Let me walk you through the workflow using screenshots"
Advantage: Still visual, you control the narrative

Option 3: Pivot to Business Discussion

Script: "Rather than troubleshoot live, let's cover the business case today, and I'll schedule a dedicated technical demo with your engineers"
Advantage: Saves the meeting, shows professionalism

❌ Never Do This: Spend 10+ minutes troubleshooting in front of executives. You lose credibility and waste their time. Pivot immediately.

🎬 Scenario: Demo Crashes

You're 10 minutes into a Tantor demo with a CIO. Suddenly, the demo environment freezes. The CIO is watching. What do you do?

Option A

"Let me try refreshing... one moment... let me check my connection..."

(Troubleshoot live)

Option B

"I'm sorry, we'll need to reschedule. I'll fix this and come back next week."

(Abort the meeting)

Option C

"No problem—I have a recorded demo ready. Let me show you that, and we can schedule a live technical deep-dive with your team."

(Use fallback, maintain momentum)

Option D

"These things happen in the cloud. Let me tell you about the architecture instead."

(Deflect with explanation)

💡 Why Option C is the Pro Move

"No problem": Shows confidence—this doesn't rattle you
"Recorded demo ready": Shows you're prepared for contingencies
"Schedule a live deep-dive": Creates a natural next step

Why others fail:

A: Troubleshooting live = looks unprofessional, wastes time
B: Rescheduling = loses momentum, may never happen
D: Deflecting = doesn't deliver what you promised

🎓 Knowledge Check Quiz ⏱️ 5 min

Test Your Learning

Passing Score: 4 out of 6 questions (67%)

Apply SCQA, visual design, and presentation principles.

0/6

🎯 Key Takeaways ⏱️ 3 min

Module 5, Section 2: Presentation Design & Storytelling

SCQA Framework:

Situation: Current state (facts everyone agrees on)
Complication: The problem (what changed, what's wrong)
Question: The implicit question raised
Answer: Your solution—the payoff

Visual Design Principles:

One message per slide: Two points = two slides
Action titles: State conclusions, not descriptions
Signal-to-noise: Remove everything that doesn't support the message
The Squint Test: If you can't tell what it's about from across the room, simplify

Tech-to-Business Translation:

Formula: [Technical Feature] → [So What?] → [Business Outcome]
Example: "Log-based CDC" → "Real-time data" → "Detect fraud in seconds"
Never stop at the feature—always get to the ₹ impact

Audience Adaptation:

Executives: 10-15 min, lead with ROI, 80% outcomes / 20% how
Technical: 20-30 min, show architecture, 80% how / 20% outcomes
Mixed: Layered approach—business headline → technical detail → ROI close

Slides-to-Demo Ratio:

Technical products (Tantor, Kong, HashiCorp): 20-30% slides, 70-80% demo
Services (Managed, Professional): 70-80% slides, 20-30% demo
Always provide context before demo—never just "let me show you"

Demo Failure Recovery:

Always have fallback ready: recorded demo, screenshots, or business pivot
Never troubleshoot live—pivot immediately
Use failure to create next meeting: "Let's schedule a technical deep-dive"

🎉 Section 2 Complete!

You've mastered presentation design and storytelling. Next up: Section 3 - Live Demo Execution.